Skip to content

Changes B for Issue 38 #42

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 11 commits into from
Apr 22, 2025
Merged

Changes B for Issue 38 #42

merged 11 commits into from
Apr 22, 2025

Conversation

sipke
Copy link

@sipke sipke commented Mar 24, 2025

Addresses additional items for issue 38

This should merge after pull request #41 as it is on top of those changes

  • move "If you want to contribute and port OpenAMP to your platform read more about OpenAMP porting here." to contributing page
  • add link to virtio spec in openamp-governance-and-guidelines
  • to rewrite this chapter ( remove standardization notions).
  • Avoid duplication with https://www.openampproject.org/governance/ in this pages. to determine if a part of the gouvernance should be moved ghere
  • no roadmap defined, to remove chapter
  • no platform maintainer defined, to remove chapter and/or rewrite according to gouvernance page
  • "History" to move to OpenAMp project part?
  • "input ring buffer" and "free ring buffer" is not really current terminology in Virtio lingo. Maybe just keep the standard used and available terminology.
  • It's not clear from the title of this image that it refers to the available ring buffer.
  • The fastest fix is to remove the last phrase which mentions the "referred to as a hypervisorless-virtio" statement.
  • Following short-forms should be explained somewhere - expand on openAMP specific acronyms
  • Add glossary
  • openamp examples are deprecated so move reference to reference repository
  • NXP i.MX8M Plus is also supported.

Copy link
Collaborator

@edmooring edmooring left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to go.

@arnopo
Copy link
Collaborator

arnopo commented Apr 17, 2025

@sipke
Please, could you rebase this one and #43 +#44 that I merge them?

Sipke Vriend added 11 commits April 18, 2025 08:47
Refer issue 38: OpenAMP#38
Address review comment:
move "If you want to contribute and port OpenAMP to your platform
read more about OpenAMP porting here." to contributing page
Refer issue 38: OpenAMP#38
Address review comment:
add link to the virtio spec
Refer issue 38: OpenAMP#38
Address review comment:
 to rewrite this chapter ( remove standardization notions).
Refer issue 38: OpenAMP#38
Address review comment:
 "History" to move to OpenAMp project part?
Refer issue 38: OpenAMP#38
Address review comments:
* "input ring buffer" and "free ring buffer" is not really current
terminology in Virtio lingo. Maybe just keep the standard used and
available terminology.
* It's not clear from the title of this image that it refers to the
available ring buffer.
Refer issue 38: OpenAMP#38
Address review comment:
* The fastest fix is to remove the last phrase which mentions the "referred to as a
hypervisorless-virtio" statement.
Expand on the OpenAMP specific acronyms on first usage, so they make
sense later in bullet points

Address Review comment:
* Following short-forms should be explained somewhere:
Add a link to glossary and start filling out a table of terms.
openamp examples are deprecated so move reference.
Refer issue 38: OpenAMP#38
Address review comment:
NXP i.MX8M Plus is also supported.
review change
rather than link to specific version of virtio, link to upper level
listing of all versions.
there isn't a latest version it seems, so let reader decide where to go.
@arnopo arnopo merged commit 818a526 into OpenAMP:main-next Apr 22, 2025
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants